docs: alexander is built (#262) - #324
Merged
Merged
Conversation
The guest exists, runs stacks/lab, and the documents now say so. docs/network.md gains its ImaginationLAN row — 10.0.30.40, bc:24:11 (the Proxmox 9 OUI), Ubuntu 26.04 LTS — and the note that described it as the guest `Saruman` *will* run is rewritten as the one it does. That note keeps the reason it is a guest rather than the hypervisor, because that is the part a reader will otherwise undo. The OS goes in as the release line and not `26.04.1`: POINT_RELEASE in check_docs.py rejects a third component on purpose, since a point release goes stale at the next apt upgrade and node_os_info carries the running one. Written as `Ubuntu 26.04 LTS` rather than `Ubuntu Server 26.04 LTS` to match the two rows already in the file. docs/architecture.md drops the **Not built yet** marker, which is what the marker was for. That did exactly what it was designed to do on the way out: count_alloy_agents stopped excluding the row, the count went to four, and check_docs.py failed the two places still claiming three — hardware.md, and the runbook section describing this very step, which quoted the sentence verbatim. The check does not care whether prose describes a number or asserts one, and it was right not to; the runbook now says what changes without restating it. The runbook's OS row said 24.04 where the guest runs 26.04, and its reasoning claimed the LTS ships rsyslog. 24.04 does; Ubuntu has been narrowing its default install, and a runbook cannot know what the LTS a future reader picks will do. So the claim becomes an instruction to verify — §7 already exists for exactly that, and the remedy is one apt-get line either way. What this does NOT assert: that the two file log sources are collecting. §7 answers that from the guest's own Grafana, and it is the check the OS decision was made for. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The guest exists and runs
stacks/lab. §8 of the build runbook, done.The changes
docs/network.md— the ImaginationLAN row:10.0.30.40,bc:24:11(the Proxmox 9 OUI),Ubuntu 26.04 LTS. The note that describedalexanderas the guestSarumanwill run is rewritten as the one it does, keeping the reason it is a guest and not the hypervisor — that is the part a future reader would otherwise undo.docs/architecture.md— the**Not built yet**marker comes off, which is what it was for.docs/hardware.md— three Alloy agents becomes four.The marker earned its keep on the way out
Removing it did exactly what it was designed to do:
count_alloy_agentsstopped excluding the row, the count went to four, andcheck_docs.pyfailed two places still claiming three —hardware.md, and the runbook section describing this very step, which quoted the sentence verbatim.The check does not care whether prose is describing a number or asserting one, and it was right not to. The runbook now says what changes without restating it.
Two smaller corrections it surfaced
The OS is recorded as
26.04 LTS, not26.04.1.POINT_RELEASErejects a third component on purpose — a point release goes stale at the nextapt upgrade, andnode_os_infocarries the running one. Written asUbuntu 26.04 LTSrather thanUbuntu Server ...to match the two rows already in that table.The runbook said 24.04 where the guest runs 26.04, and justified the choice by claiming the LTS ships rsyslog. 24.04 does; Ubuntu has been steadily narrowing its default install, and a runbook cannot know what the LTS a future reader picks will do. So the claim becomes an instruction to verify — §7 already exists for exactly that, and the remedy is one
apt-getline either way.What this deliberately does not claim
That the two file log sources are actually collecting. These rows assert the host exists and what it runs, which is verifiable. Whether
/var/log/auth.logand/var/log/syslogare being tailed is §7's question, answered from the guest's own Grafana, and it is the check the whole OS decision was made for. Still outstanding.make validatepasses.🤖 Generated with Claude Code